Subject: DLUR MIB question

From: "Michael O. Allen (919-254-4442)" <[email-masked]>
Date: Fri, 7 Oct 94 09:36:30 EDT

Ref:  Your note of Fri, 7 Oct 1994 13:28:54 +0100 (attached)

Christine,

Sorry that those states were not self-explanatory.  Here is what was
intended for those intermediate states:

pendInop

   An ACTPU arrived from the DLUS, was forwarded to the PU, the ACTPU
   response has not arrived from the PU, and the connection to DLUS has
   been lost.

pendInopActpu

   An ACTPU arrived from the DLUS, was forwarded to the PU, the ACTPU
   response has not arrived from the PU, the connection to DLUS was
   lost and reestablished, and a new ACTPU arrived from the DLUS.

These intermediate states are not strictly required by the DLUR
architecture, so there may be room for some simplification in an
implementation.  In that case, you should just use the state values
that are applicable to what you keep track of.

Mike

----------------------------- Note follows ------------------------------
From: [email-masked] (Christine Martin)
Date: Fri, 7 Oct 1994 13:28:54 +0100
To: aiw-appn-reference <@MIT.EDU:[email-masked]>
Subject: DLUR MIB question
Cc: [email-masked]

I have a quick question on the DLUR MIB.  For the dlurPuTable, the
dlurPuStatus field can take a number of different values.  Most of the
values are pretty self-explanatory, but could you clarify the use of
pendInop and pendInopActpu?

Thanks!

--
==============================================================
Christine Martin  ([email-masked])
Data Connection Limited
Telephone: +44 81 366 1177
Fax:       +44 81 367 8501
==============================================================